Skip to content

ci: raise grype severity cutoff from medium to high#518

Merged
JAORMX merged 1 commit intomainfrom
ci/grype-severity-cutoff-high
Apr 20, 2026
Merged

ci: raise grype severity cutoff from medium to high#518
JAORMX merged 1 commit intomainfrom
ci/grype-severity-cutoff-high

Conversation

@JAORMX
Copy link
Copy Markdown
Collaborator

@JAORMX JAORMX commented Apr 20, 2026

Summary

  • Bump the grype severity-cutoff in build-containers.yml from medium to high, so only high/critical CVEs fail the build.
  • Medium and below still run and upload to the GitHub Security tab via SARIF — they're visible, just non-blocking.

Why

Medium-severity findings in base images and transitive npm/pip deps regularly block otherwise-healthy container builds (e.g. PR #509 packaging the Pinecone MCP), often with no upstream fix available. High/critical is a more actionable gate.

Test plan

  • CI passes on this PR
  • Re-run PR feat: add Pinecone MCP server #509 (or a rebase) and confirm the build-containers job no longer fails the grype step on medium findings
  • Confirm medium/low vulns still show up in the Security tab for the affected images

🤖 Generated with Claude Code

Medium-severity vulnerabilities in base images and transitive deps
routinely block container builds (e.g. PR #509 Pinecone MCP) even when
no fix is available upstream. Only fail the build on high/critical
findings; medium and below still upload to the Security tab via SARIF.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@JAORMX JAORMX merged commit 5c06b61 into main Apr 20, 2026
2 checks passed
@JAORMX JAORMX deleted the ci/grype-severity-cutoff-high branch April 20, 2026 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants